Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes Service Discovery Custom Settings #313

Merged
merged 4 commits into from
Oct 2, 2024

Conversation

shakeeb-upstart
Copy link
Contributor

Closes #311

  • Added configNamespace in Kubernetes settings object, so that users can create different settings based on config path

  • Added "Settings" object to KubernetesApiServiceDiscovery constructor so that users are able to provide their different settings for discovery

…can create different settings based on config path

- Added "Settings" object to KubernetesApiServiceDiscovery constructor so that users are able to provide their different settings for discovery
@pjfanning pjfanning added this to the 1.1.0 milestone Sep 26, 2024
@pjfanning
Copy link
Contributor

I'm ok with merging this if other reviewers are happy to proceed.

@raboof
Copy link
Member

raboof commented Sep 26, 2024

(failure is #216 again)

Copy link
Member

@raboof raboof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks!

Settings being an Extension still looks a bit strange to me, but that's not introduced in this PR, so fine to leave that as-is.

@raboof
Copy link
Member

raboof commented Sep 26, 2024

@Roiocam did you want to do a re-review or are we OK to (Squash and) merge?

Copy link
Contributor

@pjfanning pjfanning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@shakeeb-upstart
Copy link
Contributor Author

@pjfanning @raboof can we merge this?

@raboof raboof merged commit cca5ce0 into apache:main Oct 2, 2024
15 checks passed
@raboof
Copy link
Member

raboof commented Oct 2, 2024

Yes, thanks!

This change will likely be released with Pekko Management 1.1.0. This release is not yet planned, and we have some other releases still in the pipeline before this one, so it's hard to predict a timeline. If you want to try this feature early, you can use a development snapshot (https://repository.apache.org/content/repositories/snapshots/org/apache/pekko/) at your own risk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kubernetes Namespace Service Discovery
4 participants